Does this include souls for the Armadillo, the Bogged, and the Breeze? Asking as they are not ticked off yet in #1010.

Armadillo, Bogged, and Breeze souls were added in #1054

This uses the player motion library, which is a potential issue since it's the first time adding a non-gm4 library as a dependency. AFAIK there is no way for our dependency checker functions (now automatically generated based on beet.yaml) to account for external libraries and disable the module if an unsupported version of player motion is installed. At the very most, the dashing pneuma would change behavior, which isn't that big of a deal. Should this be addressed before merging this change?

I'm not too keen on relying on external data pack libraries

I don't think relying on external libraries is a bad thing, as long as we properly pin the version or copy it into our sources. But I'm more wondering why this library is suddenly necessary and wasn't in the previous version. Could we not update OoA to 1.21.5 without this new mechanic?

The library isn't necessary, but it provides a much better UX and UI. The previous system locked the player into the trajectory, not allowing them to move away from the initial dash (since it makes the player ride an armor stand which is given motion) and it also used weird armor stand motion which broke. Instead of fixing the broken armor stand motion I decided it was better to do it the "proper" way with player motion.

I can try to fix dashing without player motion if we don't wanna deal with it for this update.

Using the player_motion library seems fine, as long as:

1. We won't run into problems when multiple modules try to rely on it
2. We make sure the build is still 100% reproducible
3. We can handle updating the library to a new version
4. We can handle when player_motion is included in a non-GM4 data pack, possibly a different version

Okay, this PR now adds player motion as a GM4 library (lib_player_motion) which has the following differences:

• the targeted player motion library is locked to one specific version of the player motion library (v1.4.2 rn since it's the latest)
• the library uses gm4_player_motion instead of player_motion namespaces
• #minecraft:load has been deleted to allow for our lantern load and versioning plugin to handle load
• Function tags #gm4_player_motion:launch_xyz and #gm4_player_motion:launch_looking are added to allow for version-checked function calls similar to our other libraries
• The marker spawned at 0 0 0 (for trig) is spawned (and targeted) with a different UUID to prevent conflict with the normal library marker

This handles all 4 criteria specified in the last message.

Additionally, this PR now adds a new plugin which refactors external libraries to prefix namespaces with "gm4_" and deletes any #minecraft:load and #minecraft:tick function tags that are used.

The player motion library has been "forked" (copied over manually) to use lantern load and our forceloaded chunk. Full changes can be found in the README of lib_player_motion.

I'm not entirely sure if the licensing is done correctly. MIT doesn't require us to list the changes made (like GPL3 does), so I think we should be fine just putting the original MIT license file in the data/gm4_player_motion folder? But I don't think that would be carried onto the download zip since it only carries over the main LICENSE file from the library root folder. Or do we just add the copyright onto our license file?